Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1416

reference
698-tree-1
name
1416
tree-preservation-order

undefined

698-tpo-1
uprn
address-text
point
POINT (-1.010222 50.881344)
geometry
MULTIPOLYGON (((-1.010166 50.881338,-1.010168 50.881349,-1.010176 50.881359,-1.010189 50.881367,-1.010204 50.881372,-1.010222 50.881374,-1.010239 50.881372,-1.010255 50.881367,-1.010268 50.881360,-1.010276 50.881350,-1.010279 50.881338,-1.010277 50.881327,-1.010269 50.881317,-1.010257 50.881309,-1.010241 50.881304,-1.010223 50.881302,-1.010206 50.881304,-1.010190 50.881309,-1.010177 50.881316,-1.010169 50.881326,-1.010166 50.881338)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL